home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
kermit.columbia.edu
/
kermit.columbia.edu.tar
/
kermit.columbia.edu
/
newsgroups
/
misc.20041116-20060924
/
000271_scottac@nb.sympatico.ca_Sun Mar 19 14:56:12 2006.msg
< prev
next >
Wrap
Internet Message Format
|
2006-09-27
|
3KB
Path: newsmaster.cc.columbia.edu!panix!newsfeed.media.kyoto-u.ac.jp!newsfeed.news2me.com!wns13feed!worldnet.att.net!207.35.177.252!nf3.bellglobal.com!ursa-nb00s0.nbnet.nb.ca!53ab2750!not-for-mail
From: "Scott Caissie" <scottac@nb.sympatico.ca>
Newsgroups: comp.protocols.kermit.misc
References: <uGRPf.40748$VV4.591414@ursa-nb00s0.nbnet.nb.ca> <kLSPf.9392$X.1010@news-wrt-01.rdc-nyc.rr.com> <slrne10fck.8bc.fdc@sesame.cc.columbia.edu> <RqZPf.40942$VV4.594211@ursa-nb00s0.nbnet.nb.ca> <slrne10uul.jul.fdc@sesame.cc.columbia.edu>
Subject: Re: closing a macro completely upon connect
Lines: 55
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 6.00.2900.2180
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180
X-RFC2646: Format=Flowed; Original
Message-ID: <H81Qf.41050$VV4.597519@ursa-nb00s0.nbnet.nb.ca>
Date: Thu, 09 Mar 2006 21:31:19 GMT
NNTP-Posting-Host: 156.34.15.45
X-Complaints-To: abuse@aliant.net
X-Trace: ursa-nb00s0.nbnet.nb.ca 1141939879 156.34.15.45 (Thu, 09 Mar 2006 17:31:19 AST)
NNTP-Posting-Date: Thu, 09 Mar 2006 17:31:19 AST
Organization: Aliant Internet
Xref: newsmaster.cc.columbia.edu comp.protocols.kermit.misc:15523
just a little correction to prevent any misunderstanding. When I was saying
"Normally all bug fixes are free. Enhancements cost. This unique situation
would involve us paying this company to pay (you guys) for the fix. And they
are already behind on a lot of bug fixes of their own." I was referring to
the company we are leasing from rather than yourselves.
"Frank da Cruz" <fdc@columbia.edu> wrote in message
news:slrne10uul.jul.fdc@sesame.cc.columbia.edu...
> On 2006-03-09, Scott Caissie <scottac@nb.sympatico.ca> wrote:
> : ya but unfortunatly our terminal emulation is leased. I have to make due
> : with whats avialable to us as is.
> : We have no administrator within the company for this software. I'm the
> only
> : one who actually bothered to research this stuff. I've developed many
> : improvements. But some I have to put on hold due to that. Normally all
> bug
> : fixes are free. Enhancements cost. This unique situation would involve
> us
> : paying this company to pay for the fix. And they are already behind on a
> lot
> : of bug fixes of their own.
> :
> Bug fixes AND upgrades were free from the very beginning up until the
> layoffs
> occurred 3 years ago. The problem now is that the expertise is no longer
> under one roof. At least the critical fixes *are* available, albeit at a
> fee.
>
> : But back on topic, how to properly deal with a macro from becoming
> nested
> : too much.
> :
> I don't think there is a workaround to the "macros on keys" bug, other
> than
> the awkward one mentioned in the bug list:
>
> 735. Macros on Keys broken
>
> In versions 1.1.21 through 2.1.3, when a SET [TERMINAL] KEY definition
> includes a macro invocation, then pressing the key while in the
> Terminal screen returns to the command screen (and in some cases might
> also fail to execute the macro). A workaround would be to:
>
> define myconnect connect /synchronous
> (make the connection with SET PORT, DIAL, or SET HOST)
> if success do myconnect
>
> This is fixed in the next release.
>
> As I said, I'm working on getting approval to issue a new release.
>
> - Frank